Add explicit setting for "no email security" #402
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ng on the env var not being set at all
Jest Coverage
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The present mechanism for configuring that your email server uses no security is to omit the
DJANGO_EMAIL_SECURITYsetting from.envaltogether. This is somewhat brittle as upgrades and some initial installation scenarios can either leave the variable wrongly set or modify it (from no security to TLS, as that is the default setting for new installs).This PR allows an explicit
to represent an active choice of "no security" in a way that's less likely to be accidentally overwritten.
Closes #401